Skip to content

[DSpace-CRIS] Inverse Relations via Authority Framework (Frontend)#5134

Open
FrancescoMolinaro wants to merge 5 commits intoDSpace:mainfrom
4Science:task/main/DURACOM-445
Open

[DSpace-CRIS] Inverse Relations via Authority Framework (Frontend)#5134
FrancescoMolinaro wants to merge 5 commits intoDSpace:mainfrom
4Science:task/main/DURACOM-445

Conversation

@FrancescoMolinaro
Copy link
Contributor

@FrancescoMolinaro FrancescoMolinaro commented Feb 20, 2026

References

Description

Add new component for tabbed relations in item page.
The new relations are based on a scope parameter which represent the authority of the item in question.
Visually the component still uses the standard search page and is identical:

image

The new relations can be activated via a flag param in the default.app.config.ts, inside the item config:

showAuthorithyRelations

if true the ui components will use the new authority based relations.

Instructions for Reviewers

List of changes in this PR:

Add new UI component for new scope/authority based relations

Include guidance for how to test or review your PR. This may include: steps to reproduce a bug, screenshots or description of a new feature, or reasons behind specific changes.

Checklist

This checklist provides a reminder of what we are going to look for when reviewing your PR. You do not need to complete this checklist prior creating your PR (draft PRs are always welcome).
However, reviewers may request that you complete any actions in this list if you have not done so. If you are unsure about an item in the checklist, don't hesitate to ask. We're here to help!

  • My PR is created against the main branch of code (unless it is a backport or is fixing an issue specific to an older branch).
  • My PR is small in size (e.g. less than 1,000 lines of code, not including comments & specs/tests), or I have provided reasons as to why that's not possible.
  • My PR passes ESLint validation using npm run lint
  • My PR doesn't introduce circular dependencies (verified via npm run check-circ-deps)
  • My PR includes TypeDoc comments for all new (or modified) public methods and classes. It also includes TypeDoc for large or complex private methods.
  • My PR passes all specs/tests and includes new/updated specs or tests based on the Code Testing Guide.
  • My PR aligns with Accessibility guidelines if it makes changes to the user interface.
  • My PR uses i18n (internationalization) keys instead of hardcoded English text, to allow for translations.
  • My PR includes details on how to test it. I've provided clear instructions to reviewers on how to successfully test this fix or feature.
  • If my PR includes new libraries/dependencies (in package.json), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.
  • If my PR includes new features or configurations, I've provided basic technical documentation in the PR itself.
  • If my PR fixes an issue ticket, I've linked them together.

@tdonohue tdonohue added new feature DSpace-CRIS merger This ticket/PR relates to the merger of DSpace-CRIS into DSpace. labels Feb 20, 2026
@tdonohue tdonohue moved this to 🙋 Needs Reviewers Assigned in DSpace 10.0 Release Feb 20, 2026
@tdonohue
Copy link
Member

tdonohue commented Feb 20, 2026

@FrancescoMolinaro : Could you specify which DSpace-CRIS differences this PR relates to? I think it's important to be clear to reviewers which features or architectural changes are in each PR, and it's unclear to me which one(s) this references

@FrancescoMolinaro FrancescoMolinaro marked this pull request as ready for review March 4, 2026 17:12
@artlowel artlowel requested a review from KevinVdV March 12, 2026 17:03
@github-actions
Copy link

Hi @FrancescoMolinaro,
Conflicts have been detected against the base branch.
Please resolve these conflicts as soon as you can. Thanks!

@tdonohue
Copy link
Member

@FrancescoMolinaro : This appears to require backend PR DSpace/DSpace#11963 , so I've updated the description to note that

@tdonohue tdonohue changed the title [DSpace-CRIS] Porting of authority based relations components [DSpace-CRIS] Inverse Relations via Authority Framework (Frontend) Mar 13, 2026
Copy link
Member

@KevinVdV KevinVdV left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I made an initial review of this PR, I found 2 small issues, see details below.

Issue 1

The backend add support for the following pages to make use of this search box:

  • people
  • org units
  • projects,
    But in the PR the only place the ds-authority-related-entities-search is used is in the person entity.

Issue 2

The new authority framework UI component is enabled by default, this will cause with backwards compatibility. Can you modify the configuration so that the authority framework is optional (so it is the same as in the REST code)

@github-project-automation github-project-automation bot moved this from 🙋 Needs Reviewers Assigned to 👀 Under Review in DSpace 10.0 Release Mar 19, 2026
@FrancescoMolinaro
Copy link
Contributor Author

FrancescoMolinaro commented Mar 19, 2026

Hi @KevinVdV , thanks for the feedback, I have updated the item pages so that also OrgUnit and Projects have their configurations as on the backend.
In addition I have set the functionality to be disabled by default.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

DSpace-CRIS merger This ticket/PR relates to the merger of DSpace-CRIS into DSpace. new feature

Projects

Status: 👀 Under Review

Development

Successfully merging this pull request may close these issues.

[DSpace-CRIS] Data model finalization work (Hierarchical metadata, virtual metadata, etc)

3 participants